Skip to content

Conversation

@arvinxx
Copy link
Collaborator

@arvinxx arvinxx commented Jul 24, 2025

BREAKING CHANGES: bump peerDependencies antd >= v6

Summary by CodeRabbit

  • 新功能

    • 样式系统现已支持通过 cssVar 提供的 CSS 变量,提升了主题灵活性和自定义能力。
  • 依赖更新

    • 升级了 antd 依赖至 6.0.0-alpha.1 预发布版本。
    • 更新了测试环境为 happy-dom,提升测试兼容性和稳定性。
    • 其他相关依赖如 vitevitest 也进行了版本升级。
  • 文档

    • 示例代码已同步更新以展示新的样式变量用法。
  • 测试

    • 优化了部分测试用例中的样式断言,增强测试的准确性和一致性。
  • 构建与配置

    • 更新了 GitHub Actions 工作流,采用新版 Node.js 和 pnpm 版本,提升构建与发布效率。
    • 调整了测试配置,使用绝对路径别名,优化模块解析。

BREAKING CHANGES: bump peerDependencies antd >= v6
@coderabbitai
Copy link

coderabbitai bot commented Jul 24, 2025

📝 Walkthrough

Walkthrough

本次变更将样式相关逻辑从依赖 token 切换为使用 cssVar,并在样式工厂与主题 Hook 之间传递 cssVar。Ant Design 依赖升级至 6.0.0-alpha.1,并同步调整类型定义和样式工厂工具,保证 cssVar 在各层级正确传递和使用。测试断言中的颜色格式也进行了统一调整,测试环境配置改为 happy-dom,路径别名改为绝对路径。GitHub Actions 工作流升级了关键动作版本和 Node.js 版本。StyleProviderProps 接口移除了 autoClear 属性。

Changes

文件/路径分组 变更摘要
docs/demos/api/createStyles/default.tsx useStyles 钩子中样式逻辑由 token 切换为 cssVar,去除 px 后缀。
package.json antd 依赖升级至 6.0.0-alpha.1,@ant-design/cssinjs、vite、vitest 版本升级,新增 happy-dom 依赖。
src/factories/createStyles/index.ts createStylesFactory 中解构和传递 theme.cssVar。
src/factories/createStyles/types.ts CreateStylesUtils 接口新增 cssVar: FullToken 属性。
src/hooks/useAntdTheme.ts useAntdTheme 用 antd 的 theme.useToken(),返回 token 和 cssVar。
src/factories/createStyleProvider/index.tsx StyleProviderProps 接口移除 autoClear 属性。
src/factories/createThemeProvider/ThemeSwitcher.test.tsx 测试断言中背景色由 #fff 改为 #ffffff。
tests/functions/createGlobalStyle.test.tsx 测试断言中颜色由大写十六进制改为小写十六进制(#1677FF → #1677ff)。
tests/functions/createStyles.test.tsx 测试断言调整:背景色断言注释,颜色由大写十六进制改为小写,RGB 改为命名色。
tests/functions/extractStaticStyle.test.tsx 测试断言中 data-antd-version 由匹配模式改为固定字符串 "6.0.0-alpha.1"。
vitest.config.ts 测试环境由 jsdom 改为 happy-dom,路径别名改为绝对路径,新增 node:path resolve 导入。
.github/workflows/{preview,release,test}.yml GitHub Actions 工作流升级 checkout、pnpm、setup-node 等动作版本,Node.js 版本升级。
CHANGELOG.md 新增 4.0.0-alpha.1 版本,支持 Ant Design 6 CSS 变量,peer 依赖升级。

Sequence Diagram(s)

sequenceDiagram
    participant App
    participant useStyles
    participant createStylesFactory
    participant useAntdTheme
    participant antdTheme

    App->>useStyles: 调用 useStyles()
    useStyles->>createStylesFactory: 获取样式工具(含 cssVar)
    createStylesFactory->>useAntdTheme: 获取主题(token, cssVar)
    useAntdTheme->>antdTheme: 调用 theme.useToken()
    antdTheme-->>useAntdTheme: 返回 { token, cssVar }
    useAntdTheme-->>createStylesFactory: 返回 { token, cssVar }
    createStylesFactory-->>useStyles: 返回样式工具(含 cssVar)
    useStyles-->>App: 返回样式对象
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰
变量新添 cssVar,
主题升级步步夸。
antd 六代初登场,
代码清新无繁杂。
小兔审阅乐开花,
未来样式更优雅!
🌿✨🐇

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch alpha

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions
Copy link

github-actions bot commented Jul 24, 2025

🎊 PR Preview b922a94 has been successfully built and deployed to https://ant-design-antd-style-preview-pr-198.surge.sh

🕐 Build time: 99.196s

🤖 By surge-preview

@socket-security
Copy link

socket-security bot commented Jul 24, 2025

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updated@​vitest/​coverage-v8@​0.34.6 ⏵ 3.2.49910070 +599100
Updatedvitest@​0.34.6 ⏵ 3.2.49710077 +199100
Updatedvite@​4.5.14 ⏵ 6.3.595 +11008199100
Addedantd@​6.0.0-alpha.18610010010080
Addedhappy-dom@​18.0.1991008891100
Added@​ant-design/​cssinjs@​2.0.0-alpha.89910010094100

View full report

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (1)
docs/demos/api/createStyles/default.tsx (1)

11-12: cssVar 值格式变化的重要说明

从 token 迁移到 cssVar 时,值的格式发生了重要变化:

  • token 属性返回原始值(如 8px
  • cssVar 属性返回 CSS 自定义属性字符串(如 var(--ant-border-radius-lg)

这个 demo 正确展示了如何直接使用 cssVar 值,无需添加像素后缀。这是一个重要的 API 变化,建议在文档中明确说明。

Also applies to: 17-17, 23-24, 30-31

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a132d47 and cd838b0.

📒 Files selected for processing (5)
  • docs/demos/api/createStyles/default.tsx (1 hunks)
  • package.json (2 hunks)
  • src/factories/createStyles/index.ts (2 hunks)
  • src/factories/createStyles/types.ts (1 hunks)
  • src/hooks/useAntdTheme.ts (1 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (2)
src/factories/createStyles/types.ts (1)
src/types/theme.ts (1)
  • FullToken (71-71)
src/hooks/useAntdTheme.ts (2)
src/types/theme.ts (1)
  • AntdTheme (67-69)
src/hooks/useAntdStylish.ts (1)
  • useAntdStylish (11-22)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: preview
🔇 Additional comments (7)
package.json (1)

99-99: 确认 antd v6.0.0-alpha.1 未被弃用但仍为预发布版

从 npm Registry 查询可知
• description: “An enterprise-class UI design language and React components implementation”
• deprecated: null

虽然该版本未被标记为弃用,但仍属 alpha 预发布,可能存在稳定性和兼容性风险。建议:

  1. 在生产环境部署前进行充分回归和冒烟测试
  2. 在文档中说明如何回退至 v5.x 系列以防紧急问题
  3. 关注 antd 官方 v6 稳定版发布时间表,并在合适时机升级至正式版
src/factories/createStyles/types.ts (1)

19-19: 类型定义正确且一致

添加 cssVar: FullToken 类型定义是正确的,与现有的 token 属性保持一致。这样设计合理,因为 cssVar 和 token 都代表相同的设计令牌结构,只是格式不同(CSS 变量 vs 常规值)。

src/factories/createStyles/index.ts (2)

60-61: cssVar 解构和传递实现正确

从 theme 中正确解构出 cssVar 并与其他属性分离,实现符合预期。解构模式确保了 cssVar 和 token 的正确分离。


78-78: 确认 cssVar 可用性
useAntdTheme 已通过 theme.useToken() 解构并返回 cssVartheme 对象确实包含该属性,无需额外修改。

src/hooks/useAntdTheme.ts (2)

4-4: 正确使用 antd v6 的 theme API

从 antd 导入 theme 并使用 theme.useToken() 是正确的迁移方式,符合 antd v6 的新 API 设计。


11-11: useMemo 依赖数组更新正确

正确更新了 useMemo 的依赖数组,包含新增的 cssVar 参数,确保当 cssVar 变化时能正确重新计算。

docs/demos/api/createStyles/default.tsx (1)

9-9: 正确展示 cssVar 使用方式

demo 正确地从 token 迁移到 cssVar,为用户提供了清晰的使用示例。


export const useAntdTheme = (): AntdTheme => {
const token = useAntdToken();
const { token, cssVar } = theme.useToken();
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

验证 theme.useToken() 返回 cssVar

确认 antd v6.0.0-alpha.1 的 theme.useToken() 确实返回 cssVar 属性。


🌐 Web query:

Does Ant Design v6.0.0-alpha.1 theme.useToken() method return cssVar property?

💡 Result:

In Ant Design v6.0.0-alpha.1, the theme.useToken() method does not return CSS variables directly. Instead, it provides JavaScript objects containing the resolved token values. This approach allows for dynamic theming and customization within your React components.

However, it's important to note that Ant Design's theming system does not natively support the use of CSS variables within tokens. This limitation arises because the theming algorithm does not interpret CSS variables, which can lead to issues when attempting to use them in tokens. (github.com)

To incorporate CSS variables into your Ant Design theming, you can utilize the @ant-design/cssinjs package. This package enables the use of CSS variables in your styles, providing a more flexible and dynamic theming solution. By integrating @ant-design/cssinjs, you can define your theme tokens as CSS variables and apply them throughout your application. (github.com)

In summary, while theme.useToken() in Ant Design v6.0.0-alpha.1 does not return CSS variables, you can achieve CSS variable-based theming by incorporating the @ant-design/cssinjs package into your project.

Citations:


修复 theme.useToken() 解构

Ant Design v6.0.0-alpha.1 中,theme.useToken() 并不返回 cssVar 属性,直接解构会导致 cssVar 值为 undefined

请处理以下位置:

  • 文件src/hooks/useAntdTheme.ts
    行号:8
    当前
    const { token, cssVar } = theme.useToken();
    建议
    • 若不依赖 CSS 变量,将解构改为:
      const { token } = theme.useToken();
    • 若需使用 CSS 变量,请安装并配置 @ant-design/cssinjs,并通过其 API 获取 cssVar(例如在入口文件或主题配置中启用 CSSinJS 变量支持)。
🤖 Prompt for AI Agents
In src/hooks/useAntdTheme.ts at line 8, theme.useToken() is destructured to get
cssVar, but in Ant Design v6.0.0-alpha.1 cssVar is not returned and will be
undefined. To fix this, remove cssVar from the destructuring and only extract
token if CSS variables are not needed. If CSS variables are required, set up
@ant-design/cssinjs properly and obtain cssVar through its API instead of
directly from theme.useToken().

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cd838b0 and 35732f5.

⛔ Files ignored due to path filters (3)
  • tests/components/__snapshots__/ThemeProvider.test.tsx.snap is excluded by !**/*.snap
  • tests/functions/__snapshots__/createInstance.test.tsx.snap is excluded by !**/*.snap
  • tests/functions/__snapshots__/createStyles.test.tsx.snap is excluded by !**/*.snap
📒 Files selected for processing (6)
  • package.json (4 hunks)
  • src/factories/createThemeProvider/ThemeSwitcher.test.tsx (2 hunks)
  • tests/functions/createGlobalStyle.test.tsx (2 hunks)
  • tests/functions/createStyles.test.tsx (3 hunks)
  • tests/functions/extractStaticStyle.test.tsx (1 hunks)
  • vitest.config.ts (1 hunks)
✅ Files skipped from review due to trivial changes (2)
  • tests/functions/createGlobalStyle.test.tsx
  • src/factories/createThemeProvider/ThemeSwitcher.test.tsx
🚧 Files skipped from review as they are similar to previous changes (1)
  • package.json
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: preview
🔇 Additional comments (6)
tests/functions/createStyles.test.tsx (3)

54-55: 明确 TODO 的具体要求和时间表

注释掉的背景色断言带有 "需要在 Release v4 之前恢复" 的 TODO,但缺乏具体的上下文说明。

请明确以下信息:

  1. 为什么需要暂时注释掉这个断言?
  2. v4 发布的具体时间表是什么?
  3. 恢复断言时期望的背景色值是什么?

建议在代码中添加更详细的注释说明原因,或者创建一个 issue 来跟踪这个 TODO 项目。


221-221: 颜色格式标准化符合预期

将十六进制颜色值从大写 #1677FF 改为小写 #1677ff 是合理的标准化,符合 CSS 规范和大多数项目的约定。


264-264: 使用命名颜色提高可读性

将颜色值从 RGB 格式 'rgb(255, 0, 0)' 改为命名颜色 'red' 提高了代码可读性,这是一个很好的改进。

vitest.config.ts (3)

1-1: 正确导入路径解析工具

添加 resolve 导入以支持绝对路径别名配置是正确的做法。


10-11: 使用绝对路径提高配置可靠性

将别名路径从相对字符串改为使用 resolve(__dirname, './src') 的绝对路径是最佳实践,可以避免相对路径解析问题。


7-7: 请在本地执行以下脚本验证 happy-dom 环境下的测试兼容性

由于 CI 沙箱中未安装 Vitest,建议在本地环境先安装依赖并运行测试:

#!/bin/bash
# 安装项目依赖
npm ci

# 使用 npx 运行所有测试并输出详细报告
npx vitest run --reporter=verbose

# 检查代码中是否存在依赖 jsdom 特定功能的测试用例
rg -A 5 -B 5 "jsdom|JSDOM" .

运行完成后,请确认所有测试均通过且没有检出对 jsdom 的直接依赖。若在本地环境中测试通过,则可以安心合并该改动。

Comment on lines +56 to +58
expect(item.tag).toMatch(
/<style data-rc-order="prepend" data-rc-priority="-9999" data-antd-version="6.0.0-alpha.1">\s*/,
);
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

考虑测试断言的维护性

将版本断言从语义版本模式改为硬编码的 "6.0.0-alpha.1" 可能会在 antd 版本更新时导致测试失败。

建议考虑以下方案之一:

  1. 使用更灵活的正则表达式匹配 6.x 版本:/6\.\d+\.\d+(-\w+\.\d+)?/
  2. 从 package.json 中动态读取 antd 版本进行断言
  3. 如果确实需要精确版本控制,请确保在版本升级时同步更新此测试
-      expect(item.tag).toMatch(
-        /<style data-rc-order="prepend" data-rc-priority="-9999" data-antd-version="6.0.0-alpha.1">\s*/,
-      );
+      expect(item.tag).toMatch(
+        /<style data-rc-order="prepend" data-rc-priority="-9999" data-antd-version="6\.\d+\.\d+(-\w+\.\d+)?">\s*/,
+      );
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
expect(item.tag).toMatch(
/<style data-rc-order="prepend" data-rc-priority="-9999" data-antd-version="6.0.0-alpha.1">\s*/,
);
expect(item.tag).toMatch(
/<style data-rc-order="prepend" data-rc-priority="-9999" data-antd-version="6\.\d+\.\d+(-\w+\.\d+)?">\s*/,
);
🤖 Prompt for AI Agents
In tests/functions/extractStaticStyle.test.tsx around lines 56 to 58, the test
assertion uses a hardcoded antd version "6.0.0-alpha.1" which reduces
maintainability. To fix this, replace the hardcoded version in the regex with a
more flexible pattern that matches any 6.x version, such as
/6\.\d+\.\d+(-\w+\.\d+)?/, or alternatively, dynamically read the antd version
from package.json and use it in the assertion. This will prevent test failures
when the antd version updates.

arvinxx and others added 5 commits July 24, 2025 20:16
# [4.0.0-alpha.1](v3.7.1...v4.0.0-alpha.1) (2025-07-24)

### ✨ Features

* Support antd v6 cssVar ([cd838b0](cd838b0))

### 💥 BREAKING CHANGES

* bump peerDependencies antd >= v6
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🔭 Outside diff range comments (1)
.github/workflows/preview.yml (1)

21-31: 缺少 step ID,steps.preview_step 引用将报错
afc163/surge-preview 步骤未声明 id,后续通过 steps.preview_step.outputs.preview_url 无法解析,CI 会在运行时抛出 Cannot read property 'outputs' of undefined

修复示例:

-      - uses: afc163/surge-preview@v1
+      - id: preview_step
+        uses: afc163/surge-preview@v1
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 35732f5 and f739af5.

⛔ Files ignored due to path filters (1)
  • tests/functions/__snapshots__/createInstance.test.tsx.snap is excluded by !**/*.snap
📒 Files selected for processing (6)
  • .github/workflows/preview.yml (1 hunks)
  • .github/workflows/release.yml (2 hunks)
  • .github/workflows/test.yml (1 hunks)
  • CHANGELOG.md (1 hunks)
  • package.json (5 hunks)
  • src/factories/createStyleProvider/index.tsx (1 hunks)
✅ Files skipped from review due to trivial changes (3)
  • .github/workflows/test.yml
  • .github/workflows/release.yml
  • src/factories/createStyleProvider/index.tsx
🚧 Files skipped from review as they are similar to previous changes (1)
  • package.json
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
CHANGELOG.md

5-5: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3

(MD001, heading-increment)

🔇 Additional comments (3)
.github/workflows/preview.yml (3)

9-9: checkout 升级到 v4 ✔️
升级到 actions/checkout@v4 与官方推荐保持一致,没有额外风险。


12-15: 请确认 pnpm-10 与现有 lockfile 兼容性
仓库若仍保留旧版 pnpm-lock.yaml,直接拉升到 pnpm 10 可能触发 lockfile 重写或解析失败,尤其是在 workspace 场景下。建议本地以 pnpm 10 重新生成 lockfile 并提交,或在 CI 前增加 pnpm -v 断言。


16-19: Node.js 22 非 LTS,需确认依赖兼容
当前生态大多数包的 CI 仍以 Node 20 LTS 为基线。将 CI 主版本直接切到 22 可能导致编译或 native 模块安装失败。建议:

  1. 增加 matrix,保留 2022 并观测。
  2. 或在 release/workflow 中仅使用 20,在实验性 job 中验证 22

Comment on lines +3 to +11
# [4.0.0-alpha.1](https://github.com/ant-design/antd-style/compare/v3.7.1...v4.0.0-alpha.1) (2025-07-24)

### ✨ Features

- Support antd v6 cssVar ([cd838b0](https://github.com/ant-design/antd-style/commit/cd838b0))

### 💥 BREAKING CHANGES

- bump peerDependencies antd >= v6
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

修复标题层级,避免 markdownlint 报错

版本标题使用了 #,与文件中其他版本标题的 ## 不一致,且导致 #### 直接跳过一级标题层级,被 markdownlint 标记为 MD001。请统一为二级标题。

-# [4.0.0-alpha.1](https://github.com/ant-design/antd-style/compare/v3.7.1...v4.0.0-alpha.1) (2025-07-24)
+## [4.0.0-alpha.1](https://github.com/ant-design/antd-style/compare/v3.7.1...v4.0.0-alpha.1) (2025-07-24)
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
# [4.0.0-alpha.1](https://github.com/ant-design/antd-style/compare/v3.7.1...v4.0.0-alpha.1) (2025-07-24)
### ✨ Features
- Support antd v6 cssVar ([cd838b0](https://github.com/ant-design/antd-style/commit/cd838b0))
### 💥 BREAKING CHANGES
- bump peerDependencies antd >= v6
## [4.0.0-alpha.1](https://github.com/ant-design/antd-style/compare/v3.7.1...v4.0.0-alpha.1) (2025-07-24)
### ✨ Features
- Support antd v6 cssVar ([cd838b0](https://github.com/ant-design/antd-style/commit/cd838b0))
### 💥 BREAKING CHANGES
- bump peerDependencies antd >= v6
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

5-5: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3

(MD001, heading-increment)

🤖 Prompt for AI Agents
In CHANGELOG.md around lines 3 to 11, the version title uses a single '#' header
which is inconsistent with other version titles using '##' and causes
markdownlint MD001 errors due to skipping heading levels. Change the version
title header from '#' to '##' to maintain consistent heading levels and fix the
linting issue.

@arvinxx arvinxx marked this pull request as draft August 11, 2025 01:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants